All contributors have signed the DCO ✍️ ✅
_{Posted by the DCO Assistant Lite bot.}

Greptile Summary

This PR fixes a bug where DataDesigner.__init__ would silently overwrite a caller's pre-configured logging setup (e.g. debug level) with the interface's default INFO config. The fix introduces a module-level _logging_configured flag in logging.py that is set after a successful configure_logging() call, and guards the default-logging call in _initialize_interface_runtime() behind an is_logging_configured() check.

• logging.py: adds _logging_configured = False, sets it to True at the end of configure_logging(), and exposes is_logging_configured().
• data_designer.py: wraps the default configure_logging() call in _initialize_interface_runtime() with if not is_logging_configured() so any prior configuration is preserved.
• Tests: updates test_initialize_interface_runtime_runs_once to reset _logging_configured via monkeypatch (keeping the mock assertion reliable), and adds two new tests — one unit test for the flag itself, and one end-to-end regression that verifies a DEBUG config survives DataDesigner() construction.

Important Files Changed

%%{init: {'theme': 'neutral'}}%%
sequenceDiagram
    participant User
    participant logging as data_designer.logging
    participant iface as _initialize_interface_runtime

    User->>logging: configure_logging(LoggingConfig.debug())
    logging->>logging: set handlers, levels
    logging->>logging: "_logging_configured = True"

    User->>iface: DataDesigner(...)
    iface->>iface: _interface_runtime_initialized? → False
    iface->>logging: is_logging_configured()
    logging-->>iface: True
    iface->>iface: skip configure_logging() ✓
    iface->>iface: resolve_seed_default_model_settings()
    iface->>iface: "_interface_runtime_initialized = True"
    iface-->>User: DataDesigner ready (DEBUG logging preserved)

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
sequenceDiagram
    participant User
    participant logging as data_designer.logging
    participant iface as _initialize_interface_runtime

    User->>logging: configure_logging(LoggingConfig.debug())
    logging->>logging: set handlers, levels
    logging->>logging: "_logging_configured = True"

    User->>iface: DataDesigner(...)
    iface->>iface: _interface_runtime_initialized? → False
    iface->>logging: is_logging_configured()
    logging-->>iface: True
    iface->>iface: skip configure_logging() ✓
    iface->>iface: resolve_seed_default_model_settings()
    iface->>iface: "_interface_runtime_initialized = True"
    iface-->>User: DataDesigner ready (DEBUG logging preserved)

_{Reviews (1): Last reviewed commit: "fix: preserve preconfigured logging" | Re-trigger Greptile}

recheck

Stale PR reminder

This PR has had failing checks for 7 days without activity.

Failing checks: check

Please push an update or leave a comment if you're still working on this.
Otherwise, this PR will be automatically closed in 7 days.

To prevent auto-close, add the keep-open label.

Issue #388 has been triaged. The linked issue check is being re-evaluated.

Thanks for jumping on this, this fixes a pretty easy-to-miss logging footgun. I reviewed the runtime init path and the new logging state tracking. The core behavior looks good, but I'd like one small clarification before merge.

is_logging_configured() only tracks calls through data_designer.logging.configure_logging(). It won't detect users who configured logging through the standard Python APIs, like logging.basicConfig() or manually attached root handlers, so DataDesigner() would still call configure_logging() and replace those handlers.

Please add a short docstring/comment making that scope explicit, or broaden the check if you want this to cover general Python logging setup too. The current fix is fine for the linked issue, but the helper name reads a bit broader than what it actually guarantees.

Focused tests and a smoke check passed locally. Once that expectation is tightened up, this looks good to merge from my side.

Following up on my comment above: the current fix handles the narrow repro from #388 where the caller uses data_designer.logging.configure_logging() before constructing DataDesigner.

There is a related case discussed later in #388 that this does not cover yet: applications that configure logging through stdlib APIs before using Data Designer. For example, if a caller uses logging.basicConfig() or attaches custom root handlers, DataDesigner() can still call DD's default configure_logging(), clear those root handlers, and replace the application's logging setup.

I think the lowest-risk incremental direction is to make DD's automatic runtime logging setup opt-out explicitly, which also matches the direction Mike suggested on #388. Something like:

• add an auto_configure_logging: bool = True keyword to DataDesigner.__init__
• pass it into _initialize_interface_runtime(...)
• only call DD's default configure_logging() when both auto_configure_logging is True and DD logging has not already been configured
• add tests for:
  • default behavior still configures DD logging
  • DataDesigner(..., auto_configure_logging=False) preserves existing root handlers
  • prior data_designer.logging.configure_logging(...) is still preserved

That should keep standalone behavior unchanged while giving embedded/library users a reliable way to prevent DD from taking over process logging.